This pull request improves the clarity and completeness of the documentation around CRE report generation, delivery, and verification, especially for workflows using HTTP. It introduces a new guide for verifying CRE reports offchain, clarifies the sender/receiver model for report delivery, and updates related guides and navigation to reflect these changes.

Documentation improvements for CRE report lifecycle:

• Added a new sidebar entry and guide for "Verifying CRE Reports Offchain," making it easier for users to find instructions on how to verify report signatures and metadata when receiving reports via HTTP or other offchain channels. [1] [2]
• Expanded and clarified the explanations of what a CRE report is, where it comes from, and how it should be handled on both the sender and receiver sides in the HTTP submission guides (submitting-reports-http-go.mdx). This includes a new section on the expected JSON payload for offchain verification and a detailed sender flow. [1] [2]
• Updated the main HTTP client index to introduce the CRE report concept, explain the sender/receiver pattern, and link to the new offchain verification guide.

Clarifications and cross-linking in report generation and submission guides:

• Improved the guides for generating reports with single values and structs to clearly define CRE reports, explain the difference between onchain and HTTP delivery, and direct users to the appropriate verification steps for each delivery method. [1] [2] [3]
• Added summary tables and sections in the EVM client overview guides to show where reports can be delivered after generation, with links to the relevant submission and verification guides for both onchain and HTTP paths. [1] [2]
• Updated the onchain submission guide to clarify that onchain verification is built-in, and to direct users who need HTTP delivery to the appropriate guides, including the new offchain verification documentation.

Minor updates:

• Updated metadata fields such as lastModified to reflect recent changes.
• Improved consistency and accuracy in cross-references, code identifiers, and terminology throughout the guides. [1] [2]